Add inbound message size validation#1821
Open
AkramBitar wants to merge 1 commit into
Open
Conversation
AkramBitar
force-pushed
the
feature/incoming-message-size-limits
branch
from
94226b5 to
cad0e2f
Compare
AkramBitar
force-pushed
the
feature/incoming-message-size-limits
branch
from
cad0e2f to
5898dc6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a max message-size check at the one place all inbound messages pass through (ReceiveRawWithTimeout), so signature replies, auditor payloads, and distribution acks are rejected before deserialization. Oversized payloads fail fast with ErrMessageTooLarge; malformed ones are still caught by the existing envelope validation. Default limit 100 MiB, configurable.